-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[AMDGPU] Cluster export instruction in PostRA Scheduler #141399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@llvm/pr-subscribers-backend-amdgpu Author: Carl Ritson (perlfu) ChangesDAG mutation needs to be applied post-RA to maintain order established during pre-RA scheduler. Full diff: https://github.com/llvm/llvm-project/pull/141399.diff 1 Files Affected:
diff --git a/llvm/lib/Target/AMDGPU/AMDGPUTargetMachine.cpp b/llvm/lib/Target/AMDGPU/AMDGPUTargetMachine.cpp
index e24d8481408ad..7479703ce353a 100644
--- a/llvm/lib/Target/AMDGPU/AMDGPUTargetMachine.cpp
+++ b/llvm/lib/Target/AMDGPU/AMDGPUTargetMachine.cpp
@@ -1129,6 +1129,7 @@ GCNTargetMachine::createPostMachineScheduler(MachineSchedContext *C) const {
getOptLevel() >= CodeGenOptLevel::Less) &&
EnableVOPD)
DAG->addMutation(createVOPDPairingMutation());
+ DAG->addMutation(createAMDGPUExportClusteringDAGMutation());
return DAG;
}
//===----------------------------------------------------------------------===//
|
This is a pre-commit test for llvm#141399.
35b663e
to
0eb864e
Compare
Maybe this can only apply post-RA? |
This is a pre-commit test for #141399.
DAG mutation needs to be applied post-RA to maintain order established during pre-RA scheduler.
0eb864e
to
fba6127
Compare
I think we do need to do this pre-RA as well so RA understands the liveness of the register used for the exports. |
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/208/builds/1486 Here is the relevant piece of the build log for the reference
|
DAG mutation needs to be applied post-RA to maintain order established during pre-RA scheduler.